<html>
<head><meta charset="utf-8"><title>lolbench-try-run · t-compiler · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/index.html">t-compiler</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/lolbench-try-run.html">lolbench-try-run</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="163120080"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/lolbench-try-run/near/163120080" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> anp <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/lolbench-try-run.html#163120080">(Apr 11 2019 at 17:28)</a>:</h4>
<p><span class="user-mention" data-user-id="116009">@nikomatsakis</span> there isn’t yet a feature on lolbench to run a “try job” (also the github pages site is down bc of too much data in the repo &gt;_&lt;) but the whole suite can be run locally. there are some recommended settings in the repo read me and in the ansible scripts for reducing noise. what the remote runners execute is pretty straightforward and in those files. on a pretty fast machine the whole suite takes 6+ hours right now for a single toolchain, so prepare for some waiting. strongly recommend bare metal over VMs, the folks at packet have agreed to donate machines to lolbench but i haven’t set them up yet</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>